Building an Application with TDD, DDD and Hexagonal Architecture - Isn't it a bit too much? - Mufrid Krilic
This talk was recorded at NDC Oslo in Oslo, Norway. #ndcoslo #ndcconferences #developer #softwaredeveloper
Attend the next NDC conference near you:
Subscribe to our YouTube channel and learn every day:
/ @NDC
Follow our Social Media!
#architecture #ddd #tdd #code
Many experienced developers are longing for an opportunity to build an application from scratch. Compared to the heavy legacy applications, which are seen as filled with technical debt and incomprehensible architecture and design choices, a fresh start promises that you can finally write code and build an application "the right way."
On the other hand, experience has taught us that complexity in the code creeps in regardless. We wondered then if the very principles we based ourselves on, could actually contribute to making the code harder to read and maintain in the long run?
This presentation will show how we built a backend application for integration between three different systems based on TDD, DDD and hexagonal architecture. Along the way, we have assessed the complexity of the solution and asked ourselves some questions:
Have our decisions about isolation of the domain model and abstraction layer between the systems led to less or greater complexity?
What constitutes a domain model?
What about deliberately reduced test coverage on selected parts of the code?
The presentation
|
DevLaunch is my mentorship program where...
DevLaunch is my mentorship program where...
When you're negotiating your salary for ...
What are recent advances in the field of...
Today Quincy Larson interviews Kunal Kus...
Arrow functions don't have their own 'th...
Learn Git and GitHub from scratch with c...
freeCodeCamp runs right in the browser -...
This is part two of our two episode seri...